<rss version="2.0" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
    <channel>
        <title>Business Analyst Community &amp; Resources | Modern Analyst</title> 
        <link>https://modernanalyst.com</link> 
        <description>RSS feeds for Business Analyst Community &amp; Resources | Modern Analyst</description> 
        <ttl>60</ttl> <item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/7165/9-Effective-UX-Design-Trends-that-is-Shaping-the-Future-of-User-Experience.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=7165</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=7165&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>9 Effective UX Design Trends that is Shaping the Future of User Experience</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/7165/9-Effective-UX-Design-Trends-that-is-Shaping-the-Future-of-User-Experience.aspx</link> 
    <description>UX design is evolving fast, and the biggest shifts are no longer just about making screens look better. This article explores nine trends redefining digital experiences, from AI-driven personalization and voice interfaces to immersive 3D, adaptive layouts, minimalism, and data-informed design. It shows how UX is becoming more predictive, more human-centered, and more responsive to real behavior, while still demanding simplicity, accessibility, and thoughtful execution. For business analysts, product teams, and UX professionals, this is a useful snapshot of where user experience is heading next and what capabilities will matter most.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Mon, 20 Apr 2026 00:34:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:7165</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/7146/Provenance-UX-How-to-Specify-Why-Should-I-Believe-This-in-Product-Requirements.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=7146</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=7146&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Provenance UX: How to Specify “Why Should I Believe This?” in Product Requirements</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/7146/Provenance-UX-How-to-Specify-Why-Should-I-Believe-This-in-Product-Requirements.aspx</link> 
    <description>This article shows business analysts, systems analysts, and product managers how to build &amp;ldquo;trust into the UI&amp;rdquo; by writing practical provenance requirements for AI-enabled features. It introduces a simple Provenance Requirements Template that turns vague goals like &amp;ldquo;show sources&amp;rdquo; into testable product behavior: when to display citations (ideally tied to specific claims), how to handle conflicting sources with a clear tie-breaker, how to define freshness SLAs by claim type and what to do when data is stale, and how to support confidence/uncertainty, &amp;ldquo;what changed,&amp;rdquo; and audit exports. The takeaway is a repeatable way to specify &amp;ldquo;why should I believe this?&amp;rdquo; so answers come with receipts, stay current, and can be verified or audited when needed.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sun, 08 Feb 2026 05:02:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:7146</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/7060/Balancing-Usability-and-Security-Challenges-for-Business-Analysts.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=7060</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=7060&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Balancing Usability and Security: Challenges for Business Analysts</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/7060/Balancing-Usability-and-Security-Challenges-for-Business-Analysts.aspx</link> 
    <description>Striking a balance between usability and security is a challenging yet crucial responsibility for business analysts, demanding a blend of technical expertise, empathy, and strategic insight. By comprehending trade-offs, catering to stakeholder requirements, and adopting proactive measures, business analysts can develop systems that are both user-friendly and robust. As technologies such as AI and IoT progress, maintaining this equilibrium becomes increasingly vital, with AI-powered anomaly detection tools offering innovative ways to bolster security without compromising on usability. Successful business analysts will view this not as a zero-sum situation but as a chance to create systems that promote business success in a secure and accessible digital environment.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Mon, 20 Oct 2025 00:16:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:7060</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/7009/Keep-Your-Eyes-on-the-Interfaces.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=7009</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=7009&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Keep Your Eyes on the Interfaces</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/7009/Keep-Your-Eyes-on-the-Interfaces.aspx</link> 
    <description>Business analysts must identify external interfaces and the constraints they impose on architecture and detailed designs. Conscientious designers will ensure that all the pieces of a complex system fit together correctly across their mutual interfaces. New components that developers integrate into an existing system must also conform to established interface conventions.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Mon, 25 Aug 2025 00:00:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:7009</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6951/Improve-the-User-Experience-with-Dialog-Maps.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6951</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6951&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Improve the User Experience with Dialog Maps</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6951/Improve-the-User-Experience-with-Dialog-Maps.aspx</link> 
    <description>Many books provide guidance on how to create effective user interface displays, a vital aspect of the user&amp;rsquo;s experience with a software application. But a user often must navigate through a series of screens to perform a task. Making that flow sequence logical and efficient is also an important part of the user experience.

I&amp;rsquo;m a big fan of analysis modeling, drawing diagrams that visually represent various aspects of a software system and its requirements. One of my favorite models is the dialog map, which provides a convenient way to represent, validate, and improve how a user navigates through a user interface.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sun, 13 Jul 2025 23:31:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6951</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6270/Top-UIUX-Design-Trends-That-Will-Skyrocket-in-2023.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6270</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6270&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Top UI/UX Design Trends That Will Skyrocket in 2023</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6270/Top-UIUX-Design-Trends-That-Will-Skyrocket-in-2023.aspx</link> 
    <description>Maintaining a competitive edge and providing a positive user experience in the rapidly developing field of UI/UX or user interface and user experience design necessitates that organizations keep up with the newest trends. As we move into the year 2023, it will be increasingly important for businesses to innovate and adapt to maximize customer satisfaction and conversion rates.

A community prototype tool for UI/UX designers could command such a hefty premium. The UI/UX design field has matured into an integral part of modern businesses. Major advancements in accessibility, augmented reality, and design will be among the top UI UX developments in 2023.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 21 May 2023 21:30:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6270</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5763/Perfect-Your-Requirements-and-Designs-With-Prototypes.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5763</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5763&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Perfect Your Requirements and Designs With Prototypes</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5763/Perfect-Your-Requirements-and-Designs-With-Prototypes.aspx</link> 
    <description>&amp;nbsp; &amp;nbsp; &amp;nbsp;Designing a new product is a messy process. It involves initial brainstorming, rough concepts, false starts, and extensive refinement. Good designs begin with an identified need or opportunity, and they&amp;rsquo;re based on a solid understanding of the product&amp;rsquo;s requirements. No matter how skilled the requirements analyst is or how informed and cooperative the customer participants are, the first set of requirements they develop will be only approximately correct. It takes a process of iterative refinement and validation to accurately understand the requirements for any nontrivial product.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 02 Aug 2021 06:10:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5763</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5748/7-Characteristics-of-Meaningful-User-Messages.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5748</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5748&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>7 Characteristics of Meaningful User Messages</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5748/7-Characteristics-of-Meaningful-User-Messages.aspx</link> 
    <description>Software applications, cars, kiosks, and many other products must communicate important information to users. These feedback messages most commonly contain information about errors; warnings or alerts; and task progress, completion, or confirmation . Feedback from a product is most effective when it exhibits these seven characteristics...
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sun, 27 Dec 2020 05:13:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5748</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5563/How-to-Measure-User-Experience.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5563</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5563&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>How to Measure User Experience</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5563/How-to-Measure-User-Experience.aspx</link> 
    <description>Knowing how your users behave and how they rate user experience is important, but it is very hard to learn that without various UX metrics and tools. The quality of user experience is a complex matter; you cannot use one tool to measure the whole experience, as it is built from several smaller components.
Understanding your users&amp;rsquo; attitudes and behaviors on your site is key for providing a better user experience. There are many tools and metrics out there and most of them are data-driven. That means that collecting and analyzing data from your site has never been more important than it is today.
In this article, we will take a look at how you can measure user experience on your site, and why is it so important. Also, we will share some of the tools that you can use to measure it, and what you can measure.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 16 Mar 2020 01:12:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5563</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5483/Detailed-Requirements-for-User-Interfaces-and-Reports.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5483</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5483&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Detailed Requirements for User Interfaces and Reports</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5483/Detailed-Requirements-for-User-Interfaces-and-Reports.aspx</link> 
    <description>For business analysts working in an environment where there is a gap between SMEs and the delivery of an IT-based solution for business needs, requirements are documented to bridge that gap. You are reading this because you are a business analyst responsible for documenting detailed requirements and, in the case of this article, business needs involving one or more user interfaces (UIs) or reports.

The objective of this article is to answer the question, &amp;ldquo;How much detail is necessary?&amp;rdquo; Spoiler alert &amp;ndash; quite a bit. This is to avoid, as much as possible, a BA having to go back to a SME when designers or developers have business-level questions about a UI or report. Or worse &amp;ndash; designers or developers&amp;nbsp;not&amp;nbsp;asking questions. Instead, making assumptions about what the business needs and proceeding to deliver the solution based on those assumptions.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 01 Dec 2019 23:14:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5483</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5451/Requirements-Gathering-meets-Accessibility-Needs.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5451</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5451&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Requirements Gathering meets Accessibility Needs</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5451/Requirements-Gathering-meets-Accessibility-Needs.aspx</link> 
    <description>The ethics behind accessibility is possibly not something you have considered before. I think many would categorise an accessibility tool as something that; &amp;lsquo;makes life easier&amp;rsquo;, for a disabled user. However, what we should be taking into account when designing new digital platforms is how to make sure that every single user has the same experience. This is actually a very key point as we are not even specifically talking about disabilities here.

Have you considered mobile users vs web? IOS vs Windows? Online vs Offline? These are all possible different users of your system and all deserve the same experience. It may well be that a lot of these points are non-functional requirements that come later in the development, but if you make sure you are considering them at the start, you can save yourself a lot of time and effort in the future.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sun, 06 Oct 2019 23:37:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5451</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5429/Build-Requirements-Around-Real-Journeys.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5429</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5429&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Build Requirements Around Real Journeys</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5429/Build-Requirements-Around-Real-Journeys.aspx</link> 
    <description>Let us look at it from a different angle now and derive the requirements out of the customer journeys.&amp;nbsp;&amp;nbsp;It is impossible to introduce a change... if the change is big and you try to implement it in one go.&amp;nbsp; This is the reason we tend to break any solution into smaller components. Each solution component should be small and independent enough to be changed individually in a controlled manner. So that eventually we will compose a new experience out of them. Pretty much like using a set of Lego blocks.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 22 Sep 2019 21:50:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5429</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5428/Experience-Driven-Development-Design-for-real-people.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5428</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5428&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Experience Driven Development: Design for real people</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5428/Experience-Driven-Development-Design-for-real-people.aspx</link> 
    <description>For the business, it means they not only need to understand the problem the customers are trying to solve - they need to understand that problem in a context and design a full end-to-end experience of solving it. Some people call this process &amp;ldquo;human-centered design&amp;rdquo;, some - just using common sense when designing stuff.&amp;nbsp;</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Mon, 02 Sep 2019 21:12:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5428</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5416/What-happens-when-the-BA-and-UX-worlds-collide.aspx#Comments</comments> 
    <slash:comments>3</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5416</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5416&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>What happens when the BA and UX worlds collide?</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5416/What-happens-when-the-BA-and-UX-worlds-collide.aspx</link> 
    <description>Are you a Business Analyst (BA) wondering what User Experience (UX) Design is all about and how your involvement in a design project is likely to impact your usual role? If so, I&amp;rsquo;ve also been pondering the same question for some time.</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Mon, 19 Aug 2019 01:10:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5416</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3844/Agile-User-Interface-Design.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3844</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3844&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Agile User Interface Design</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3844/Agile-User-Interface-Design.aspx</link> 
    <description>The role of design still puzzles many agile teams I work with. When should the design activities take place? Who should carry them out? How are design decisions best captured? This blog tries to answer the questions by discussing a user-centric, iterative, and collaborative design process for Scrum and Kanban teams.</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sun, 24 Sep 2017 04:01:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3844</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3766/iRise-Why-Prototyping-is-Essential-In-the-Post-Information-Age.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3766</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3766&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>iRise: Why Prototyping is Essential In the Post-Information Age</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3766/iRise-Why-Prototyping-is-Essential-In-the-Post-Information-Age.aspx</link> 
    <description>iRise gives Business Analysts the tools they need to communicate clearly with both the business and its stakeholders. &amp;nbsp;They use working previews that can be virtually indistinguishable from the final product. &amp;nbsp;When business analysts uses iRise to elicit and document requirements: the business analyst becomes a powerful weapon to get to the right answer, ...</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sat, 13 May 2017 16:17:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3766</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3544/Never-Forget-its-the-Customer-who-Pays-our-Salary.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3544</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3544&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Never Forget it’s the Customer who Pays our Salary!</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3544/Never-Forget-its-the-Customer-who-Pays-our-Salary.aspx</link> 
    <description>The Business Analyst is in a great position to constantly focus on the desirability of the product. &amp;nbsp;A well-defined requirement elicitation process must be focused on defining the problem the business is trying to solve for our customers. If defining the problem is the first step in your requirement process you are on the way to guaranteeing that the delivered product will provide value to your customers. Throughout the development process you will be able to monitor if the product is actually solving the problem. Additionally, your requirements should be directly related to solving the problem. It is a BA&amp;rsquo;s job to question the value of every proposed requirement that product owners want to add. If the requested feature or function is not directly related to solving the problem then it should be taken out of scope.&amp;nbsp;</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 26 Jun 2016 21:20:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3544</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3461/User-Experience-A-theoretical-perspective.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3461</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3461&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>User Experience: A theoretical perspective</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3461/User-Experience-A-theoretical-perspective.aspx</link> 
    <description>This article attempts to explore a theoretical interpretation of &amp;ldquo;User Experience&amp;rdquo;. It will explore the meaning of &amp;lsquo;User Experience&amp;rsquo; itself by focusing on the user, the technology and the resulting experience from the two interacting with each other. It will define some user experience roles relating to associated professions, and also attempt to describe the single important dynamic of user experience.</description> 
    <dc:creator></dc:creator> 
    <pubDate>Mon, 21 Mar 2016 00:17:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3461</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3376/A-Mockup-is-Worth-a-Thousand-Words.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3376</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3376&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>A Mockup is Worth a Thousand Words</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3376/A-Mockup-is-Worth-a-Thousand-Words.aspx</link> 
    <description>Developers complain that customers don&amp;rsquo;t know what they want. At the same time, customers complain about having to explain the obvious. Many projects can get stuck in this type of behavior.
Fortunately, there is a loophole. Many of the problems that business people find don&amp;rsquo;t actually require a fully working application. Often, a simple &amp;ldquo;picture&amp;rdquo; (aka mockup) is enough.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 09 Nov 2015 02:22:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3376</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3287/How-not-to-get-lost-in-data-jungle.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3287</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3287&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>How not to get lost in “data” jungle?</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3287/How-not-to-get-lost-in-data-jungle.aspx</link> 
    <description>Data migration is typically the most forgotten or underestimated component of an IT project which is the process of making a copy of data and moving it from one system to another, preferably without disrupting or disabling active business processes.
On some occasions, it is not easy to understand that a data migration is needed in the project and most of the times data migration is not seen as an item that its requirements needs to be captured during analysis phase. That&amp;rsquo;s why migration related problems begin during development or testing phase when data need is identified or when the data from the old system refuses to fit properly into your new user interfaces or business rules despite the transportation of the old data. 
For a successful project, the need of a data migration and its requirements must to be identified early beginning of analysis phase and further actions should be reflected to project plan accordingly. But how? 
Data migration strategies are a whole different detailed topic and they will not be mentioned here but capturing the essentials of data nature is a life-saver activity which is the targeted idea of this work.


1.&amp;nbsp;Will you need a data migration?
Identify it during elicitation phase if possible. If not, analysis phase is also ok but be careful and just identify the need as earlier as possible. 
Ask data related simple questions. 

    Do your requirements mention from the systems need to be shut down? If yes, does this system keeps any data?
    Is your project a replacement project for an old system? If yes, does this system keeps any data?
    Do your requirements mention from entities that are already used in your company&amp;rsquo;s systems? In order to use that data do your new system&amp;rsquo;s data model needs to keep them as well. Watch out, it may mean also a nasty synchronization!

If one of answers is yes, you will need a potential data migration. Just continue to get more details.


2.&amp;nbsp;How to capture requirements and define business rules?
If you determine that you need a data migration, be careful and specify at least following details in your analysis. &amp;nbsp;
2.1&amp;nbsp;Identify if your company have multiple data sources for that entities. If yes, determine the master and the fate of other systems&amp;rsquo; data. You will see how many systems you are dealing with. It is important to know how and where data is stored, backed up, and if it is archived.
2.2&amp;nbsp;Data profiling: Data profiling is a &amp;ldquo;must have&amp;rdquo; activity to understand what are specs of the material you will be working on. Conduct profiling activities and classify the data, such as data with missing unique ID&amp;rsquo;s or missing first name and last name or false data such as numeric values as first name and other useful information like length, type, candidate for primary key, etc. Results of the profiling will guide you to design user interfaces and capture business rules.
2.3&amp;nbsp;Do you need data cleansing? According the data profiling, you will see if you need cleansing activities and what will be the final structure of the data you will be working on. Also you will be able to clarify cleansing related activities on the project timeline which will provide a cleaner vision for the project timeline.
If your answer is no, definitely check the section 2.6.
2.4&amp;nbsp;Data structures must be well understood if your project requires design of user interfaces or data forms. Consider data structures while determining dynamic user interfaces or form context.
For example, old system may store the phone number and its extension in one field by separating data by &amp;ldquo;&amp;ndash;&amp;ldquo;. This means two numbers are stored in one field and you should consider such constraints while you are designing a new interface with multiple fields on section 2.8 or determine ways to separate phone number and its extension effectively while moving the data as mentioned on section 2.7.
2.5&amp;nbsp;Fate of the historical data: &amp;nbsp;Take into account if historical data will be migrated or not. It may affect your user interfaces or business processes.
2.6&amp;nbsp;Fate of the missing or dirty data: After profiling, most probably you will see that some of your data is not clean or adequate to use in further actions. For example, you are working on sensible customer data and national identity number is mandatory but some records do not have identity numbers. It will cause you problems to pinpoint the customer or you will face further problems if this information is mandatory to display customer on the screen.&amp;nbsp; Even worse, if you have validations based on the identity number such as debt control or billing, the system will not be able to conduct such validations.
Always check whether data ownership belongs to a specific business unit. If yes, let them decide to the fate of data.

    Decide whether the data is just enough to use or will it cause problems to conduct business processes. Will you migrate such data? If yes, sections 2.8 and 2.10 will be highly important for you.
    Is it possible to clean or enhance problematic data somehow? If yes, how? Determine the way and related requirements.
    If you decide not to move such data, always consult with your business unit for possible further actions. They may need to find the customer and inform him/her legally according his/her account status or they may need another manual/automation processes.&amp;nbsp;

2.7&amp;nbsp;Data mapping is basically the activity of creating a map of the existing data model by matching each entity&amp;amp;field with the future data model. Each entity should be mapped correctly and in details to be able to move data successfully. The map is an essential item of data migration strategy which is a whole another topic and not be mentioned here in details.
Based on the mapping, you can see the gap between your legacies and your future and you can use the information on section 2.8
2.8&amp;nbsp;Screen validations and rules: Results of sections 2.2-2.7 will give you clear information about user interface validations and potential need of new business processes.
2.8.1&amp;nbsp;Screen validations?

    Define entity specs such as type and length based on the profiling results, the information will guide you to design potential data forms.
    Define the rules for the gap. If entities are not matching neatly, define UI standards and validation rules accordingly. Such as, will be these entities optional or if two different data are kept in one field, will you continue to collect and display them together?

2.8.2&amp;nbsp;New processes is needed? If you decided to transport problematic data; 

    You may need to create new processes to correct such data. For example if the identity number is mandatory and your customer update process originally does not allow to update the number, in order to enable the correction of the customer information, you may need the define rules such as displaying identity number field editable.
    You may create new processes to alert the system or trigger different actions.

2.9&amp;nbsp;Define security &amp;amp; security measures such as encryption. If data needs to be migrated encrypted, general rules shall be set during analysis phase.
2.10&amp;nbsp;Define migration acceptance criteria such as data quality, migration duration etc. if it will cause termination on your services
2.11&amp;nbsp;Define the fate of the legacy data: Will you continue to keep the data on the legacy systems? If yes, determine whether a synchronization is needed with the new system or not? How long the data should be kept on legacy system? What are maintenance rules?
&amp;nbsp;
3.&amp;nbsp;&amp;nbsp;&amp;nbsp; What is next?
Of course, plan the future! All answers will guide you for further activities which need to be added to the project plan in details. Identifying these steps at the beginning will prevent you from future unexpected surprises and definitely will help to close the project on time.
3.1&amp;nbsp;Rehearsals
A clean migration needs rehearsals where you can have a look at your situation.
3.2&amp;nbsp;Testing scenarios
Requirements need to be tested and since migration activity creates its own requirements, testing scenarios should cover these requirements as well.
Author:&amp;nbsp;Aylin Şen, Senior Business Analyst</description> 
    <dc:creator>aylinsen</dc:creator> 
    <pubDate>Thu, 28 May 2015 16:49:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3287</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2981/Improving-Data-Quality-User-Interface-Design-and-Functional-Requirements.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2981</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2981&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Improving Data Quality: User Interface Design and Functional Requirements</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2981/Improving-Data-Quality-User-Interface-Design-and-Functional-Requirements.aspx</link> 
    <description>Of all the reasons for data quality problems, I find user interface design issues to be the most interesting. This may be because it is tied to the software requirements, and I have worked as a requirements analyst for a number of years.</description> 
    <dc:creator>moorefo1</dc:creator> 
    <pubDate>Thu, 03 Jul 2014 04:01:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2981</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2669/A-Prototype-is-Nothing-More-Than-a-Picture.aspx#Comments</comments> 
    <slash:comments>6</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2669</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2669&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>A Prototype is Nothing More Than a Picture</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2669/A-Prototype-is-Nothing-More-Than-a-Picture.aspx</link> 
    <description>Sure, you put a lot of time into creating a prototype, a mockup, screenshot, or wireframe (are there any other names for the user interface drawing I’ve missed?). You may have drawn it on a whiteboard, in VISIO, or even used a requirements tool to create it. At the end of the day, no matter how much time you spend on it, it’s nothing more than a picture. And those of you who have worked in IT know developers cannot code and create a solution solely from a picture.&amp;#160;</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 07 Jul 2013 15:22:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2669</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2606/BA-and-UX-specialist-A-winning-combination-for-superior-results-in-software-projects.aspx#Comments</comments> 
    <slash:comments>6</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2606</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2606&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>BA and UX specialist: A winning combination for superior results in software projects</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2606/BA-and-UX-specialist-A-winning-combination-for-superior-results-in-software-projects.aspx</link> 
    <description>But what about user experience or interaction designers? Does every software project truly need a UX/UI specialist (or team of specialists)? Or could this aspect of the solution be taken care by the collaboration between the BA and the development team?</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 24 Jun 2013 01:20:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2606</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1892/Business-Analysis-and-User-Experience.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1892</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1892&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Business Analysis and User Experience</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1892/Business-Analysis-and-User-Experience.aspx</link> 
    <description>At UC Berkeley there has been an increasing awareness of the importance of business analysis (BA) and user experience (UX) in the software development lifecycle. In this article we will discuss the advantages of involving BA and UX practitioners in your development process, when and how to involve them, and the similarities and differences between the two professions.
</description> 
    <dc:creator>speeditonline</dc:creator> 
    <pubDate>Mon, 04 Jul 2011 10:08:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1892</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1735/Are-you-ready-to-wear-your-UX-hat-when-duty-calls.aspx#Comments</comments> 
    <slash:comments>32</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1735</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1735&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Are you ready to wear your UX hat when duty calls?</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1735/Are-you-ready-to-wear-your-UX-hat-when-duty-calls.aspx</link> 
    <description>In an ideal world, all software projects would have an interaction designer or user experience (UX) specialist working with the team to ensure that the product is designed in a way that truly satisfies the needs of end-users. In a software project with separate business analyst and interaction designer roles, the work of these professional is complementary</description> 
    <dc:creator>speeditonline</dc:creator> 
    <pubDate>Mon, 14 Mar 2011 04:06:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1735</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1216/Working-with-Various-Personalities-among-Stakeholders.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1216</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1216&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Working with Various Personalities among Stakeholders</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1216/Working-with-Various-Personalities-among-Stakeholders.aspx</link> 
    <description>Smooth stakeholder participation is integral to the success of any project. Sometimes stakeholders hold information that is essential to thorough requirements discovery, so it is important that they be forthcoming. Other stakeholders must sign off on requirements as being final in order for a project to move forward, so it is important that they be decisive and willing to let go the discovery stage of a project.</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Tue, 30 Mar 2010 04:39:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1216</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1045/From-Research-to-Implementation--6-Usability-Considerations-for-Better-Mobile-UI-Design.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1045</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1045&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>From Research to Implementation - 6 Usability Considerations for Better  Mobile UI Design</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1045/From-Research-to-Implementation--6-Usability-Considerations-for-Better-Mobile-UI-Design.aspx</link> 
    <description>Although it may seem obvious that the User Interface (UI) directly impacts usability, and therefore satisfaction, Business Analysts often find themselves focusing on functional requirements to ensure end user satisfaction. Mainly, this is due to the non-functional requirements, like usability, being dictated by existing technology or process within the organization. However, research into mobile user interfaces is placing the focus back on the usability requirements as the main driver of user satisfaction.</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Thu, 06 Aug 2009 04:01:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1045</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/940/The-Creative-Business-Analyst--Part-2-Generating-Solution-Ideas.aspx#Comments</comments> 
    <slash:comments>5</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=940</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=940&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The Creative Business Analyst - Part 2, Generating Solution Ideas</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/940/The-Creative-Business-Analyst--Part-2-Generating-Solution-Ideas.aspx</link> 
    <description>A lot of people think that coming up with solutions to business problems is the hardest part about being a business analyst – particularly when working with a client who knows more about the business than you ever will. Don’t believe it, after all you’ve already made considerable progress in understanding the problem – and your understanding is based on level-headed analysis rather than a potentially emotional interpretation by your client.
Now it’s time to look for solutions – to be creative and think outside the square. In this paper we’ll offer a few tips and techniques for getting the creative juices flowing. We’ll show you that anyone can be creative and that solutions can come from the most unexpected places – you don’t have to be a subject matter expert to come up with valid, workable solutions to business problems.</description> 
    <dc:creator>pddean</dc:creator> 
    <pubDate>Mon, 25 May 2009 03:51:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:940</guid> 
    <enclosure url="https://modernanalyst.com:443/Portals/0/Public%20Uploads/Creative_Business_Analyst_2.PDF" length="279400" type="application/pdf" />
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/889/How-to-REALLY-engage-your-stakeholders-during-use-case-modeling.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=889</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=889&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>How to REALLY engage your stakeholders during use case modeling</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/889/How-to-REALLY-engage-your-stakeholders-during-use-case-modeling.aspx</link> 
    <description>In this article, I&#39;ll be discussing some other requirements gathering methods that complement use case modeling and should be used to ensure your requirements gathering goes swimmingly.

In particular, I&#39;ll be mentioning storyboards, wireframes and prototypes.
I&#39;ll also cover what level of quality and detail you should adopt when applying these techniques.</description> 
    <dc:creator>alex_papworth</dc:creator> 
    <pubDate>Sat, 21 Mar 2009 17:30:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:889</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/216/Best-Careers-2008--UsabilityUser-Experience-Specialist-Executive-Summary.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=216</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=216&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Best Careers 2008 - Usability/User Experience Specialist: Executive Summary</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/216/Best-Careers-2008--UsabilityUser-Experience-Specialist-Executive-Summary.aspx</link> 
    <description>U.S. News and World Report published their list of&amp;#160;Best Careers for 2008 - and Usability/User Experience Professional is one of the listed professions.&amp;#160; This is a business analysis related discipline with many business analysts also playing the role of UI designer.

&quot;Usability specialists make sure that products, especially technical ones, are easy and pleasurable to use. How? First, they observe and interview potential users to identify their needs and preferences. After a prototype is developed, they watch and interview potential users again and suggest revisions. Not surprisingly, the job outlook for usability specialists is strong. The number of new, complex products is proliferating, and many of them demand a usability specialist.&quot;
Author: Marty Nemko, U.S. News &amp;amp; World Report</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Mon, 07 Jan 2008 20:27:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:216</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/198/Functional-Specification--a-Tutorial.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=198</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=198&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Functional Specification - a Tutorial</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/198/Functional-Specification--a-Tutorial.aspx</link> 
    <description>What Is A Functional Specification? 
Functional specifications (functional specs), in the end, are the blueprint for how you want a particular web project or application to look and work. It details what the finished product will do, how a user will interact with it, and what it will look like. By creating a blueprint of the product first, time and productivity are saved during the development stage because the programmers can program instead of also working out the logic of the user-experience. It will also enable you to manage the expectations of your clients or management, as they will know exactly what to expect. 

Why write a Functional Spec? 
A key benefit of writing up a Functional Spec is in streamlining the development process. The developer working from the spec has, ideally, all of their questions answered about the application and can start building it. And since this is a spec that was approved by the client, they are building nothing less than what the client is expecting. There should be nothing left to guess or interpret when the spec is completed...and this, in a nut, explains my love affair with the Functional Spec. 

Who writes a Functional Spec? 
The functional spec should be written by someone who is not involved in any other aspect of the project. You will want somebody who is very familiar with user-interface issues and web design, familiar enough with technology to know its limitations and capabilities, and someone who is a very skilled and detailed writer. While writing a spec, you will spend much of your time imagining how a user might use a certain feature and how they may navigate their way through the information. Not only do you need to map this world out visually, but you also have to write out in great detail what this world does; all the while, balancing everything within the current technological limitations and business demands. The functional spec writer&#39;s sole concern is marrying the user-experience with the various departmental, business, and technical requirements of the project.&amp;#160;

Author: Allen W. Smith</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sun, 02 Dec 2007 06:18:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:198</guid> 
    <enclosure url="http://www.mojofat.com/tutorial/functional_spec_tutorial.pdf" length="-1" type=";charset=utf-8" />
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/122/User-Interface-Design-Tips-Techniques-and-Principles.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=122</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=122&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>User Interface Design Tips, Techniques, and Principles</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/122/User-Interface-Design-Tips-Techniques-and-Principles.aspx</link> 
    <description>A fundamental reality of application development is that the user interface is the system to the users. What users want is for developers to build applications that meet their needs and that are easy to use. Too many developers think that they are artistic geniuses &amp;ndash; they do not bother to follow user interface design standards or invest the effort to make their applications usable, instead they mistakenly believe that the important thing is to make the code clever or to use a really interesting color scheme. Constantine points out that the reality is that a good user interface allows people who understand the problem domain to work with the application without having to read the manuals or receive training. 


User interface design important for several reasons. First of all the more intuitive the user interface the easier it is to use, and the easier it is to use and the less expensive to use it. The better the user interface the easier it is to train people to use it, reducing your training costs. The better your user interface the less help people will need to use it, reducing your support costs. The better your user interface the more your users will like to use it, increasing their satisfaction with the work that you have done. In this article I discuss:

    Tips and Techniques
    UI Design Principles
    Concluding Remarks

Author: Scott Ambler</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sat, 29 Sep 2007 02:28:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:122</guid> 
    <enclosure url="http://www.ambysoft.com/essays/userInterfaceDesign.html" length="-1" type="text/html; charset=UTF-8" />
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6/UML-Activity-Diagrams-Detailing-User-Interface-Navigation.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>UML Activity Diagrams: Detailing User Interface Navigation</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6/UML-Activity-Diagrams-Detailing-User-Interface-Navigation.aspx</link> 
    <description>The author illustrates how to use UML Activity Diagrams to capture and communicate the details of user interface navigation and functionality, and explain three stereotypes: presentation, exception, and connector. 
Author: Ben Lieberman</description> 
    <dc:creator>host</dc:creator> 
    <pubDate>Tue, 01 May 2007 17:05:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6</guid> 
    
</item>

    </channel>
</rss>